A radio button macro based on Using Radio Button solution by Eric Shulman

\define radio-field(fieldname values-filter)
<$list filter="$values-filter$" variable=value>
   <$radio field="$fieldname$" value=<<value>> > <<value>></$radio>
</$list>
\end

• Example

How can we create a simple edit toolbar button to insert a time stamp?

You can do it by a simple tiddler like this:

caption: CurrentTime
condition: [<targetTiddler>!has[type]] [<targetTiddler>type[text/vnd.tiddlywiki]]
description: Insert Current Time
icon: $:/core/images/tip
shortcuts: 
tags: $:/tags/EditorToolbar
title: $:/core/ui/EditorToolbar/Time

<$action-sendmessage
	$message="tm-edit-text-operation"
	$param="replace-selection"
	text=<<now>>
/>

How to use a two way view template?

Use $list widget with emptyMessage parameter and pass the second viewtemplate by emptyMessage parameter.

Example

Use a viewtemplate for all tiddlers tagged with parent as bellow

• if they also tagged with second format them as Template1
• else format them as Template2

<$list filter="[is[current]tag[parent]]">
<$list filter="[<currentTiddler>tag[second]]" emptyMessage={{Template2}}>
{{Template1}}
</$list>
</$list>

The second filter will return an empty result set if the current tiddler is not tagged by second. Then, in Template2 you’d have the template that is only displayed for tiddlers tagged parent and Template1 is displayed for those tiddler tagged both with parent and second.

A possible solution would be to add a new editor preview pane that contains a plain text editor so that you could switch to it to perform spell checking and correction.

To do so:

• Create a new tiddler called $:/_EditorPreview
• Tagged $:/tags/EditPreview, add a caption field containing Spell check, and the following content:

<$edit-text tiddler=<<currentTiddler>> class="tc-spell-check-preview"/>

<style>
.tc-spell-check-preview {width:100%;}
</style>

Then select “Spell check” as the editor preview.

It is needed to click on the preview editor textarea in order to activate spell checking and make the dotted underlines visible.

Look at: $:/_EditorPreview

Add a new button to page controls to create a new tiddler with predefined tag and contents

The below description explain step by step how to add a new button to pagecontrols including appearance in tools sidebar tab

<$button class=<<tv-config-toolbar-class>> tooltip="Add new study tiddler">
   <$list filter="[<tv-config-toolbar-icons>match[yes]]">
    <span class="chunk">{{$:/core/images/new-button}}</span>
   </$list>
   <$list filter="[<tv-config-toolbar-text>match[yes]]">
      <span class="tc-btn-text"><$text text="New Study"/></span>
   </$list>
   <$action-sendmessage $message="tm-new-tiddler" tags="study" text={{AddStudyTemplate}}/>
</$button>

The "Page Controls" buttons that appear at the top of the sidebar (e.g., "new tiddler", "control panel", "save changes", etc.) are not stored in a single tiddler. Rather, each button definition has it's own tiddler, and these tiddlers are all tagged with "$:/tags/PageControls" to indicate that they should appear in that part of the Sidebar.

To define your own button, create a new tiddler (e.g., "MyButton")

1) First, add the $:/tags/PageControls tags to that tiddler. 2) Next, enter your button definition into the text area, like this: </$list> 3) Then, add a new field named "caption". In this field, enter: New Study 4) and add another new field named "description". In this field, enter: Use this button to create a new Study tiddler with default content

Then, create a separate tiddler named "MyButtonTemplate", containing the default content you want, i.e., Source:

Findings

Abstract

Once you have defined these tiddlers, it will automatically appear as a Page Control at the top of the Sidebar.

You can re-position this button to put it the desired order alongside the other PageControls To do this, open the $:/ControlPanel (click the gear icon in the Sidebar).

1) The $:/ControlPanel has multiple levels of "tabs" for getting to the controls you need. 2) Select the "Appearance" tab (across the top). This will show a second level of tabs: "Palette", "Story View", "Theme", "Toolbars" and "Theme Tweaks". 3) Select the "Toolbars" tab. This will show a third level of tabs, displayed vertically on the left: "Edit Toolbar", "Editor Toolbar", "Page Toolbar" and "View Toolbar". 4) Select the "Page Toolbar" tab. This will display a set of checkboxes, showing all the buttons that are tagged with "$:/tags/PageControls".

If you've created your tiddler correctly, your new button will appear at the bottom of this list. To reposition it, just grab it with the mouse and drag it to move it within the list.

How to add the filter search interface into the sidebar tabs?

Follow the several steps below

1. Press the magnifying glass next to the standard sidebar search input to open $:/AdvancedSearch
2. From the $:/AdvancedSearch *shadows* tab, search for "AdvancedSearch/Filter"
3. Select "$:/core/ui/AdvancedSearch/Filter" from the search results to display that tiddler in the story
4. Edit that tiddler and add a tag: "$:/tags/SideBar"
5. You will now have a "Filter" tab in the sidebar. Select that tab to perform filter searches with the results displayed in the sidebar.

Extra goodness... there is a down-arrow button next to the filter search input. This button displays a dropdown list of pre-defined filter seaches. To add your own pre-defined filter searches to this dropdown list:

1. Create a new tiddler (e.g., "MyFilterSearch") tagged with $:/tags/Filter
2. Add a "description" field, e.g., "Apples not Oranges"
3. Add a "filter" field containing the filter search syntax, e.g., [search[apples]!search[oranges]]
4. Add a "list-before" field. Do not enter a value for this field. This will cause the entry to automatically appear before all other pre-defined filters in the list.

You can create as many custom filter searches as you like by following the above steps again, using different titles, descriptions, and filter field values.

One display issue to fix:

The list of pre-defined filters drops down to the RIGHT of the down-arrow button. In the sidebar, this typically results in part of the list flowing off the right edge of the window, making it hard to use since you can only see part of the filter descriptions. To fix this:

1. Edit the shadow tiddler

   $:/core/ui/AdvancedSearch/Filter/FilterButtons/dropdown

2. Change this line:

   <$reveal state=<<qualify "$:/state/filterDropdown">> type="popup" position="belowleft" animate="yes">`

   to

   <$reveal state=<<qualify "$:/state/filterDropdown">> type="nomatch" text="" position="belowleft" animate="yes">`

   This will shift the drop-down so it appears directly under the filter search input, rather than below the down-arrow button.

Part i: add brush loader

1. Make sure you have the highlight.js plugin installed.

2. Create a new tiddler as below. Name it whatever you like, here it is called Extra brush loader.

   • title: Extra brush loader
   • type: application/javascript
   • field name: module-type
   • field value: startup
   • with the following as text field:

   exports.after = ['load-modules'];
   
   exports.startup = function startup() {
     let hljs = $tw.modules.execute('$:/plugins/tiddlywiki/highlight/highlight.js');
   
     $tw.modules.forEachModuleOfType('highlighter', function(title, module) {
       let moduleSource = $tw.wiki.getTiddlerText(title);
       console.log('loading brush: ' + title);
       $tw.utils.evalSandboxed(moduleSource, {hljs:hljs, exports:{}}, title);
     });
   };

Part ii: add new brushes (languages)

1. Create a new tiddler with any title you like.
2. Set its type to application/javascript
3. Add a new field, name it module-type and set it to highlighter
4. Add the below line as its text field
   • if(typeof hljs !== 'undefined') {}.
5. Download the new brush (language) you like from https://cdnjs.com/libraries/highlight.js.
6. Open the brush you downloaded from step 5 above in a text editor and add its content between above curly brackets.
7. Save and reload wiki
8. For any other language to be added repeat these seven steps.

Demo

For a demo have a a look at: https://hoelz.ro/files/highlighter-example.html

Remarks

• See Add More Language Brushes to Highlight.js Plugin
• Using these procedure, you can add brushes for Fortran, Matlab, Julia, ...

How to use alias for template?

Sometimes you have a template for example in a plugin with a long name like

$:/plugins/publisher/plugin-name/template/show-raw-content

To use a friendly and small name (alias) Tobias Beer proposed to create a new tiddler as below and use it as an alias

title: tpcode

{{||$:/plugins/publisher/plugin-name/template/show-raw-content}}

Thene whenever you wish to transclude using this template use the alias name. For example to transclude myTiddler

{{myTiddler||tpcode}}

Assume you have messages stored in tiddlers, how to create a message of the day generator?

Use a pattern for naming message with sequential number and match against day number of month using the now macro

Solution

The below solution assumes

• message tiddlers have title like Message xx where xx is two digits number like 01 02. ... 31
• message tiddlers have been tagged with message (this can be any other criteria like tiddlers have a field called message, so different script can be used)

\define tid() Message $(item)$

<$set name="dd" value=<<now 0DD>> >
<$list filter="[tag[message]removeprefix[Message ]match<dd>]" variable=item>
<$transclude tiddler=<<tid>> mode=block/>
</$list>
</$set>

Remarks

• The $set widget stores the day number of month with leading zero format <<now 0DD>>
• The $list widget filters all tiddlers their title start with Message and remove the prefix to find the sequence number. Note to the trailing space in Message
• It then matches against day number
• The found item then is shown by $transclude widget. Note to mode=block
  • The tiddler parameter in $transclude is the title of message tiddler

How can I append items to list field of a tiddler?

Assume the output of a list widget should be appended to the end of items in a list field of a tiddler. The below example shows all tiddlers tagged with myTag are appended to the list field of $:/state/reference tiddler.

<$button>
<$action-listops $tiddler="$:/state/reference" $subfilter="[tag[myTag1]]"/>
Populate list field of state reference
</$button>

This works using the action-listops widget.

See also: https://tiddlywiki.com/#ActionListopsWidget

How is it possible to choose and append tiddlers to a list based on some filter criteria?

\define addmember()
<$tiddler tiddler="$:/temp/newproject"><$action-listops $field="members" $subfilter="[{!!newmember}]"/></$tiddler>
\end

Archipel is a proof of concept called that uses D3JS into Tiddlywiki to vizualize the tiddlyWiki content.

The target is to build a tool for innovation management that will help to visualize and navigate into knowledge contained into tiddlers based on their title and tags.

This Javascript widget for Tiddlywiki, uses a D3.js version 5.0 plugin to build a data visualization Knowledge map of tiddler's table of content, as zoomable circle packs.

There is another taste of using D3JS by Roland known as d3trees. Discussion on d3trees can be found on Forum

How to edit the title of a group of tiddlers?

First, a bit of history: The current version of TiddlyWiki ("TW" or "TW5") was completely re-written from the ground up several years ago to take advantage of modern browser tech such as HTML5. Additionally, in TWC, writing programmatic manipulations of tiddlers required either javascript programming or use of extra "plugins" to provide the needed syntax while in TW5, much of the programmatic syntax is provided natively within the TWCore.

First filter the tiddlers by tag and then execute the batch edit on this group. What I want to do is to put something at the begining of each tiddler's title (like adding prefix) without changing the rest of the tittle. So in the end each tiddler will have the same prefix but different rest of the title.

To "filter tiddlers by tag", use the <$list> widget, like this:

<$list filter="[tag[sometag]]">
   
</$list> 

The <$list> widget uses the filter to find all the matching tiddlers and then loops through all the matches and sets the value of the <<currentTiddler>> variable to each title, in turn. By default, the <$list> widget will simply output the value of the <<currentTiddler>> resulting in the display of titles of all the matching tiddlers. To make the widget do something else, you need to add more syntax within the enclosing <$list>...</$list> that references the <<currentTiddler>> variable to act on each tiddler (e.g., setting a specified field value in the <<currentTiddler>>)

For example, if you wanted to add/update a field named matched to "true", you would use the <$action-setfield> widget, like this:

<$list filter="[tag[sometag]]">
   <$action-setfield $tiddler=<<currentTiddler>> matched="true"/>
</$list>

However, the above code is NOT enough to get the job done. Because the <$action-setfield> widget changes stored tiddler values, it requires a user-initiated trigger event to start the process. To achieve this, you can enclose the above <$list>...</$list> loop within a <$button> widget, like this:

<$button>
   BUTTON TEXT
   <$list filter="[tag[sometag]]">
      <$action-setfield $tiddler=<<currentTiddler>> matched="true"/>
   </$list>
</$button>

So... for your this case, you might think that the code would be something like:

<$button>
   BUTTON TEXT
   <$list filter="[tag[sometag]]">
      <$action-setfield $tiddler=<<currentTiddler>> title="...NEW TITLE HERE..." />
   </$list>
</$button>

However... there are a few tricky details to consider:

First, tiddler titles are not just display text, but are used to uniquely identify each tiddler. Thus, changing a title actually copies the existing tiddler content (all fields) to another tiddler with the specified new title and renaming a tiddler actually takes TWO actions:

• first change the title (creating a new tiddler), and then
• delete the tiddler with the old title, like this:

<$button>
   BUTTON TEXT
   <$list filter="[tag[sometag]]">
      <$action-setfield      $tiddler=<<currentTiddler>> title="..." /> <!-- CREATES NEW TIDDLER -->
      <$action-deletetiddler $tiddler=<<currentTiddler>> /> <!-- REMOVES OLD TIDDLER -->  
   </$list>
</$button>

The next problem is that TW5 syntax does not do direct text manipulation "in line", so assembling the desired new title (i.e., prepending some text to the beginning of the existing title) requires use of a little "helper" macro, like this:

\define newTitle(prefix) $prefix$$(currentTiddler)$

This macro takes one parameter, "prefix". The value of the parameter is rendered into the output using the $...$ syntax (i.e., "$prefix$"). The value of the current tiddler title is already available as a variable defined in the calling scope, and is referenced using the $(...)$.

Putting it together, we get:

\define newTitle(prefix) $prefix$$(currentTiddler)$
<$button>
   BUTTON TEXT
   <$list filter="[tag[SOMETAG]]">
      <$action-setfield      $tiddler=<<currentTiddler>> title=<<newTitle "SOMEPREFIX">> />
      <$action-deletetiddler $tiddler=<<currentTiddler>> />
   </$list>
</$button>

While this works, it would be nicer if we didn't "hard code" the button label, tag to match and the prefix to be added. To do this we can move the <$button> definition into a macro, and then invoke the macro, passing in the desired values, like this:

\define newTitle(prefix) $prefix$$(currentTiddler)$

\define addPrefix(label,tag,prefix)
<$button>
   $label$
   <$list filter="[tag[$tag$]]">
      <$action-setfield      $tiddler=<<currentTiddler>> title=<<newTitle "$prefix$">> />
      <$action-deletetiddler $tiddler=<<currentTiddler>> />
   </$list>
</$button>
\end

<<addPrefix "ClickMe!" "sometag" "SomePrefix">>

That should do it.

Which pattern is better in using a button widget?

• Pattern A

<$button actions=""> ...</$button>

• Pattern B

<$button> 
actions
...
</$button>

Jeremy Ruston

I personally prefer a variant of style A where one uses a variable to store the action widgets instead of a separate tiddler:

Example

• First store the actions in a variable (here a macro)

\define my-actions()
<$action-navigate $to="$:/ControlPanel"/>
<$action-setfield $tiddler="$:/SiteTitle" $value={{{ [{$:/SiteTitle}addsuffix[!]] }}}/>
\end

• Then pass the variable to actions attribute of a $button widget.

<$button actions=<<my-actions>> >
Click me to open control panel and add an exclamation mark to the site title
</$button>

Remark

There is a priority in running actions given to $button actions attribute (pattern A) and those located inside $button widget (pattern B). see: Button Actions versus Button Inline Actions

Which filter run faster?

Assume you have more than 100 tiddlers in their tittle there is a "Demo" word! Some of them are hidden tiddlers, their name started with "$:/" what is the best filter to list them?

• Case i: two search:title

<$list filter="[search:title[exa]] -[search:title[$:]]">

</$list>

Exact Phrase Search

Example 58: Logic of Set Widget

Example: contribute to an existing branch on GitHub

Example: Contribute to an existing repository

Example:Start a new repository and publish it to GitHub

Subfilter Example

• Case ii: one search:title and negate prefix

<$list filter="[search:title[exa]!prefix[$:/]]">

</$list>

Exact Phrase Search

Example 58: Logic of Set Widget

Example: contribute to an existing branch on GitHub

Example: Contribute to an existing repository

Example:Start a new repository and publish it to GitHub

Subfilter Example

• Answer

This would probably be a little better:

<$list filter="[search:title[Demo]!prefix[$]]">

Because this way you don't make the underlying javascript look for the $ anywhere except the first character location.

Also, yours would omit:

X$:/My Demo

Which might exist if a user wanted to make a system tiddler temporarily visible in the recent tiddlers sidebar.

• Case iii

<$list filter="[!is[system]search:title[exa]]">

</$list>

Exact Phrase Search

Example 58: Logic of Set Widget

Example: contribute to an existing branch on GitHub

Example: Contribute to an existing repository

Example:Start a new repository and publish it to GitHub

Subfilter Example

Ref: Jeremy Ruston

There is a built-in filter operator is[system] for detecting system tiddlers, so a better choice would be:

[!is[system]search:title[Demo]]

Again, we filter out system tiddlers before doing the search so as to reduce the number of tiddlers that we have to search.

More discussion

1. Performance comparision between [is[current]] and <currentTiddler>
2. A fast list

How we can create tabs from complex part of texts? Assume these parts are stored in tiddler fields

<$wikify name=Résumé text='{{!!released}} {{!!author}}-Résumé'>
<$wikify name=Notes text='{{!!released}} {{!!author}}-Notes'>
<<tabs "[<Résumé>] [<Notes>]" "Click the little link">>

</$wikify>
</$wikify>

• Pitfall

Jeremy Ruston

Just to point out a pitfall of that approach – the tranclusions and will be wikified, so if you have an author Mary McManus, then their second name would be turned into a link.

If you want to display those fields without wikifying them, then use the <$text text={{!!released}}/> or <$view field="released"/> widgets.

How customize a button using the CSS class?

The $button widget has a CSS class which lets to customize the appearance of a button.

Example

Create a class to set yellow as button background and cyan on mouse hover.

Remarks

There are ready to use classes in Tiddlywiki core can be used for button for example,set class to tc-btn-invisible tc-tiddlylink to have a button look like an internal link.

What is _canonical_uri?

It lets you wrap an external tiddler into a tiddler so that you can refer to it more easily.

Example

For example, create a tiddler titled MyImage with the type image/jpeg and the _canonical_uri field set to images\anatomy.jpg. Then you can embed it as an image with [img[MyImage]] or {{MyImage}}.

The advantage of using it is that you can subsequently change the URL of the image just by changing it in a single place.

How can center table horizontally in a tiddler:

Create a tiddler tagged with $:/tags/Stylesheet and put the below css code inside it.

.tc-tiddler-body table.centered{
    margin:0 auto;
}

Other Ref: JD

Font size: 10px 11px 12px 13px 14px 15px 16px 17px 18px 19px 20px 21px 22px 23px 24px Reset

How to change the body font?

To change the body font size and line height the below two system tiddlers are used

• $:/themes/tiddlywiki/vanilla/metrics/bodyfontsize
• $:/themes/tiddlywiki/vanilla/metrics/bodylineheight

Here a code has been developed to use a select widget to handle body font sizing. To see the code edit this tiddler. Here based on the font size the line height is changed. A new range operator from TW5.1.18 is used to generate a list of font sizes. The line height here is set in two values, for small font 22px and for big font 26px line height is used.

You can change your password from your control panel.

Get to your control panel using a URL like this:

http://your-site-name.tiddlyspot.com/controlpanel/

For example if your wiki is kookmae, then use the below address

http://kookma.tiddlyspot.com/controlpanel/

1. Enter the current password
2. Choose a new password
3. Retype it and press Update

How change the background color of sidebar

Target the CSS element tc-sidebar-scrollable

Solution

1. Create a new tiddler
2. Tag it with $:/tags/Stylesheet
3. Customize tc-sidebar-scrollable

Example

To change the whole sidebar background to yellow, use the below CSS

.tc-sidebar-scrollable{
   background-color:yellow;
 }

Remarks

To adjust the wiki title and subtitle, customize the tc-sidebar-header. For example try the below CSS

.tc-sidebar-header{
 margin-top:-33px;
 }

The below css can change the sidebar tabs color:

/*sidebar tab buttons*/
.tc-sidebar-lists .tc-tab-buttons button 
{ 
 color: #FFFFFF;
 background-color: #7499DA;
}

/*sidebar tab buttons when selected*/
.tc-sidebar-lists .tc-tab-buttons button.tc-tab-selected {
 color: #FFFFFF;
 background-color: #4A7ACF;
}

How to change the background color of list-bullet button in Tiddlywiki editor toolbar?

Use the below CSS. It is possible to change the background color of all butons in a similar way.

Create a tiddler Tag it with $:/tags/Stylesheet Put the below CSS inside the tiddler body (text)

.tc-editor-toolbar > .tc-reveal > button {
     display: inline-flex;
     padding: 0; 
}

.tc-editor-toolbar button .tc-image-button {
     padding: 2px;
     font-size: 1.25em;
}

.tc-editor-toolbar button .tc-image-list-bullet {
     display: flex;
     align-items: stretch;
     justify-content: stretch;
     fill: red;
     background-color: yellow;
}

Remark

If you need to change the background color of all toolbar buttons change the last part of above CSS as below:

.tc-editor-toolbar button {
     display: flex;
     align-items: stretch;
     justify-content: stretch;
     fill: red;
     background-color: yellow;
}

Extra

you can also add a width to the svg to make it narrower, specially if it used on mobile.

.tc-editor-toolbar button .tc-image-button {
     padding: 4px 0px;
     font-size: 1.45em;
     width: 30px;
}

How to check if the macro parameter has not been passed;

Use an empty value and use a list widget to check it.

\define mm(argIn:"Empty")
<$list filter="[<__argIn__>] -Empty">
Do my job!
</$list>
\end

<$button>Check
<<mm test>>
</$button>

Remarks

• If no value for argIn passed, then it will get the default value Empty
• The filter then "[<__argIn__>] -Empty" then will return nothing and the list widget will not run
• So, the script between <$list and </$list> will be ignored.

Alternative i

A rather robust solution is proposed by BTC as below

\define macro2(param)
<$list filter="[<__param__>minlength[1]]">

Do my job!
</$list>
\end

In this method, if param has not been passed the minlength[1] returns nothing. This operator means the input should have at least one character.

Alternative ii

Bimlas in forum proposed this alternative, in that the macro is blank

\define mymacro(argIn)
<$list filter="[<__argIn__>] -[[]]">

Do my job!
</$list>
\end

<$button>Check
<<mymacro test>>
</$button>

How to check if a title refere to an existing tiddler;

Use the is or has operator.

Any of below form may be used

[is[tiddler]]   [!is[missing]] [has[title]]

Example i

The below example uses [is[tiddler]] and only lists the existing tiddlers. So, it seems c is not a tiddler.

Example ii

The below example uses [is[missing]] and only lists the non-existing tiddlers e.g. missing tiddlers. So, it seems TalhaTid is not a tiddler.

Example iii

The below example uses [has[title]] and only lists only the existing tiddlers. So, it seems TalhaTid is not a tiddler.

Left Right

See also

Checkboxes Like Radio Button

L <$checkbox field=status checked="L" unchecked="R"/>
R <$checkbox field=status checked="R" unchecked="L"/>

Left Right

See also

Checkbox with Three State

Doc also Checkbox Like Radio Button - New Solution

There are better code, see: kookma/stylesheet/tw-adjustment

*ICONS*/
html body.tc-body .tc-image-edit-button {stroke: white;fill:#000;}
html body.tc-body .tc-image-delete-button {stroke: white;fill:#ff2222;}
html body.tc-body .tc-image-cancel-button {stroke: white;fill:#ffdd55;}
html body.tc-body .tc-image-done-button {stroke: white;fill:#99ee22;}
html body.tc-body .tc-image-home-button {stroke: white;fill:#5778d8;height:20px;}
html body.tc-body .tc-image-palette {stroke: white;fill:#7897fc;}
html body.tc-body .tc-image-new-button {stroke: white;fill:#7897fc;}
html body.tc-body .tc-image-heading-1 {stroke: white;fill:#7897fc;}
html body.tc-body .tc-image-favicon {stroke: white;fill:#7897fc;}
html body.tc-body .tc-image-stamp {stroke: white;fill:#ff2277;}

How to clone tiddlers programmatically?

The purpose is to clone a tiddler silently using Tiddlywiki scripts.

\define clone(newTid,Template)
<$action-createtiddler $basetitle=$newTid$ $savetitle="temp" />
<$list filter="[<__Template__>fields[]] -title" variable=fname >
<$set name="fval" tiddler=<<__Template__>> field=<<fname>> >
<$action-setfield $tiddler={{temp}} $field=<<fname>> $value=<<fval>> />
</$set>
</$list>
\end

Remarks

• The action-createtiddler widget creates a new tiddler using basetitle and save it in a temp tiddler
• The list widgets iterated over all fileds except the title and set them for the new tiddler. These include tags, creator, created, ... fileds

Note

It is required to iterate over all fileds using this method. You can also use the method by Mark below, but it needs a unique title.

Example

The below example makes 5 clones of testTemplate.

<$button>Clone me
<$list filter="[range[1,5]addprefix[b00]]">
<$macrocall $name=clone newTid=<<currentTiddler>> Template=testTemplate />
</$list>
</$button>

Alternatives

Other solution has given here, each has pores and cons.

Solution by FrD

A code to clone a tiddler and remove filed2 from it.